Method and apparatus for facilitating creation of simulation model

ABSTRACT

A method of facilitating modeling of a system includes receiving, at a processor, an extensible markup language (XML) file corresponding to a piping and instrumentation diagram (PID) of the system; identifying, by the processor, components of the system that are described in the XML file, the XML file including information about attributes of the identified components; storing, by the processor, the information about the attributes of the identified components; and generating, by the processor, a simulation model page using syntax of a simulation modeling software environment, based on the stored information about the attributes of the identified components.

BACKGROUND 1. Field

The subject matter disclosed herein relates generally to the field ofcreating simulation models of process plants.

2. Description of Related Art

Simulation models are used to test designs for various types of systems.Simulation models include various components and interconnectionsbetween components based on the components and interconnections includedin the system being modeled. In some cases, detailed informationregarding the components and interconnections of a system are describedin a diagram. An example of such a diagram is a piping andinstrumentation diagram (PID or P&ID). A PID of a system visuallydepicts the components and interconnections of the system. A simulationengineer designing a simulation model of a system can refer tocomponents and interconnections illustrated in a PID of the system, andenter each of the illustrated components and interconnections intosimulation modeling software to create the simulation model of thesystem.

SUMMARY

According to at least some example embodiments, a method of facilitatingmodeling of a system includes receiving, at a processor, an extensiblemarkup language (XML) file corresponding to a piping and instrumentationdiagram (PID) of the system; identifying, by the processor, componentsof the system that are described in the XML file, the XML file includinginformation about attributes of the identified components; storing, bythe processor, the information about the attributes of the identifiedcomponents; and generating, by the processor, a simulation model pageusing syntax of a simulation modeling software environment, based on thestored information about the attributes of the identified components.

The system may be a process plant system.

The XML file may follow PID XML Standard ISO 15926.

The identifying may include, for each identified component, identifying,in the XML file, an XML element corresponding to the component.

The method may further include generating, by the processor, for eachidentified XML element, a component object data structure correspondingto the identified XML element.

The method may further include for each identified XML element,extracting, by the processor, attribute information of the identifiedXML element from the XML file.

The storing may include for each generated component object datastructure, storing, as one or more elements of the generated componentobject data structure, the attribute information extracted from theidentified XML element to which the generated component object datastructure corresponds.

The storing may include generating a list of strings defining theidentified components, the list of strings including information basedon the information about the attributes of the identified components.

The generating of the simulation model page may include reading from thelist of strings, by the processor, attributes of each component definedthe list of strings; creating a simulation object for each componentdefined by the list of strings, based on the read attributes; andpopulating the simulation model page with the simulation objects createdfor the components defined by the list of strings.

According to at least some example embodiments, a simulation modelgenerating apparatus includes memory storing computer-executableinstructions; and one or more processors configured to execute thecomputer-executable instructions such that the one or more processorsare configured to perform operations including, receiving an extensiblemarkup language (XML) file corresponding to a piping and instrumentationdiagram (PID) of a system, identifying components of the system that aredescribed in the XML file, the XML file including information aboutattributes of the identified components, storing the information aboutthe attributes of the identified components, and generating a simulationmodel page using syntax of a simulation modeling software environment,based on the stored information about the attributes of the identifiedcomponents.

The system may be a process plant system.

The XML file may follow PID XML Standard ISO 15926.

The one or more processors may be configured to execute thecomputer-executable instructions such that the identifying includes, foreach identified component, identifying, in the XML file, an XML elementcorresponding to the component.

The one or more processors may be configured to execute thecomputer-executable instructions such that the one or more processorsare further configured to generate, for each identified XML element, acomponent object data structure corresponding to the identified XMLelement.

The one or more processors may be configured to execute thecomputer-executable instructions such that the one or more processorsare further configured to, for each identified XML element, extractattribute information of the identified XML element from the XML file.

The one or more processors may be configured to execute thecomputer-executable instructions such that the storing includes, foreach generated component object data structure, storing, as one or moreelements of the generated component object data structure, the attributeinformation extracted from the identified XML element to which thegenerated component object data structure corresponds.

The one or more processors may be configured to execute thecomputer-executable instructions such that the storing includesgenerating a list of strings defining the identified components, thelist of strings including information based on the information about theattributes of the identified components.

The one or more processors may be configured to execute thecomputer-executable instructions such that the generating of thesimulation model page includes reading, from the list of strings,attributes of each component defined the list of strings, creating asimulation object for each component defined by the list of strings,based on the read attributes, and populating the simulation model pagewith the simulation objects created for the components defined by thelist of strings.

BRIEF DESCRIPTION OF THE DRAWINGS

The various features and advantages of the non-limiting embodimentsherein may become more apparent upon review of the detailed descriptionin conjunction with the accompanying drawings. The accompanying drawingsare merely provided for illustrative purposes and should not beinterpreted to limit the scope of the claims. The accompanying drawingsare not to be considered as drawn to scale unless explicitly noted. Forpurposes of clarity, various dimensions of the drawings may have beenexaggerated.

FIG. 1 is a block diagram illustrating an example of simulation modelgenerating apparatus according to at least some example embodiments

FIG. 2 is a flow chart illustrating an example of a simulation modelgenerating method.

FIG. 3 illustrates an example of a portion of a piping andinstrumentation diagram (PID or P&ID).

FIG. 4 illustrates an element in a portion of an extensible markuplanguage (XML) file corresponding to a PID.

FIG. 5 illustrates a method of performing object identificationaccording to at least some example embodiments.

FIGS. 6 and 7 are flow charts for illustrating a method of generating asimulation model file according to at least some example embodiments.

FIG. 8 is a flow chart illustrating an example of a simulation modelgenerating method.

DETAILED DESCRIPTION

According to at least some example embodiments, simulation modelgenerating methods and apparatuses are described, herein, in terms ofdesign documents, for example a piping and instrumentation diagram (PIDor P&ID), of a process plant and a simulation platform. However thesimulation model generating methods and apparatuses according to atleast some example embodiments can be applied to development ofsimulation models of other processes, where the design is documented interms of objects with pre-defined attributes, which can be mapped intothe attributes of objects in a simulation platform, because thesimulation model generating methods and apparatuses according to atleast some example embodiments include a|[JAMBROSE1] design tool andsimulation tool that are object based.

It should be understood that when an element or layer is referred to asbeing “on,” “connected to,” “coupled to,” or “covering” another elementor layer, it may be directly on, connected to, coupled to, or coveringthe other element or layer or intervening elements or layers may bepresent. In contrast, when an element is referred to as being “directlyon,” “directly connected to,” or “directly coupled to” another elementor layer, there are no intervening elements or layers present. Likenumbers refer to like elements throughout the specification. As usedherein, the term “and/or” includes any and all combinations of one ormore of the associated listed items.

It should be understood that, although the terms first, second, third,etc. may be used herein to describe various elements, components,regions, layers and/or sections, these elements, components, regions,layers, and/or sections should not be limited by these terms. Theseterms are only used to distinguish one element, component, region,layer, or section from another element, component, region, layer, orsection. Thus, a first element, component, region, layer, or sectiondiscussed below could be termed a second element, component, region,layer, or section without departing from the teachings of exampleembodiments.

Spatially relative terms (e.g., “beneath,” “below,” “lower,” “above,”“upper,” and the like) may be used herein for ease of description todescribe one element or feature's relationship to another element(s) orfeature(s) as illustrated in the figures. It should be understood thatthe spatially relative terms are intended to encompass differentorientations of the device in use or operation in addition to theorientation depicted in the figures. For example, if the device in thefigures is turned over, elements described as “below” or “beneath” otherelements or features would then be oriented “above” the other elementsor features. Thus, the term “below” may encompass both an orientation ofabove and below. The device may be otherwise oriented (rotated 90degrees or at other orientations) and the spatially relative descriptorsused herein interpreted accordingly.

The terminology used herein is for the purpose of describing variousembodiments only and is not intended to be limiting of exampleembodiments. As used herein, the singular forms “a,” “an,” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“includes,” “including,” “comprises,” and/or “comprising,” when used inthis specification, specify the presence of stated features, integers,steps, operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

Example embodiments are described herein with reference tocross-sectional illustrations that are schematic illustrations ofidealized embodiments (and intermediate structures) of exampleembodiments. As such, variations from the shapes of the illustrations asa result, for example, of manufacturing techniques and/or tolerances,are to be expected. Thus, example embodiments should not be construed aslimited to the shapes of regions illustrated herein but are to includedeviations in shapes that result, for example, from manufacturing.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which example embodiments belong. Itwill be further understood that terms, including those defined incommonly used dictionaries, should be interpreted as having a meaningthat is consistent with their meaning in the context of the relevant artand will not be interpreted in an idealized or overly formal senseunless expressly so defined herein.

As is discussed above, a simulation designer designing a simulationmodel of a system can refer to a PID of the system to learn thecomponents and interconnections of the process plant being modeled. ThePID can be drawn in a software (SW) environment. Similarly, thesimulation model is often developed in a SW environment. A simulationmodeling software environment may include a GUI interface through whicha simulation model may be input or defined, and/or the simulationmodeling software may accept definitions of the model through an inputfile, e.g. ASCII. According to at least some related methods ofdesigning a simulation model, a simulation engineer enters eachcomponent and interconnection illustrated in a PID into simulationmodeling software, manually (e.g., through the GUI interface). Forexample, if a PID illustrates two system elements (e.g. two tanks)connected to each other by a pipe, a software engineering would manuallyadd the two system elements to a simulation model, and manually add apipe connecting the two simulation elements to the simulation model,using simulation modeling software. Accordingly, the process of asimulation engineer manually creating a simulation model of a systembased on a PID of the system can be time consuming, particularly whenthe system is a large system with hundreds or more of components andinterconnections (e.g., a power plant system or chemical processingplant system).

Some software packages for designing PIDs include an export functionthat generates an extensible markup language (XML) code representationof the components and interconnections illustrated by a PID. Forexample, the XML code generated by PID software may follow PID XMLStandard ISO 15926.

According to at least some example embodiments, a simulation modelgenerating method includes extracting information defining thecomponents and interconnections illustrated in a PID from the XML coderepresentation of the PID, and generating a simulation model based onthe extracted information. According to at least some exampleembodiments, the simulation model is generated automatically, withoutthe need for a simulation engineer to enter each component andinterconnection illustrated in a PID into simulation modeling softwaremanually. Examples of the simulation model generating method accordingto example embodiments are discussed in greater detail below withreference to FIGS. 2-8. An example of a simulation model generatingapparatus that implements the simulation model generating method willnow be discussed below with reference to FIG. 1.

FIG. 1 is a block diagram illustrating an example of simulation modelgenerating apparatus according to at least some example embodiments.Referring to FIG. 1, a simulation model generating apparatus 200 mayinclude, for example, a data bus 259, a display unit 252, an input unit254, a storage unit 256, and a processing unit 258.

The display unit 252, input unit 254, storage unit 256, and processingunit 258 may send data to and/or receive data from one another using thedata bus 259.

The display unit 252 displays information in a graphical manner, forexample, for viewing by a user. The display unit 252 may include anydevice capable of displaying information including, for example, one ormore of a monitor, a television, a liquid crystal display (LCD) display,a light emitting diode (LED) display, a cathode ray tube (CRT) display,a projector, and the like.

The input unit 254 receives data as input, for example, from a user. Theinput unit 245 may include any device capable of receiving input dataincluding, for example, one or more of a mouse, a touchpad, atouchscreen, a keyboard, a microphone, a camera, and the like.

The storage unit 256 may be any device capable of storing data includingone or more of volatile memory, nonvolatile memory, magnetic storage,flash storage, random access memory (RAM), and the like.

The processing unit 258 may be any device that is capable of processingdata and is configured to carry out specific operations based on inputdata, or configured to execute instructions included in computerreadable code including, for example code stored in the storage unit256.

According to at least some example embodiments, the simulation modelgenerating apparatus 200 may be programmed, in terms of software and/orhardware, to perform any or all of the functions described herein asbeing performed by a simulation model generating apparatus, as well asany or all functions described below with reference to FIGS. 2-8.Consequently, the simulation model generating apparatus 200 describedherein may be embodied as a special purpose computer through softwareand/or hardware programming.

Examples of the simulation model generating apparatus 200 beingprogrammed, in terms of software, to perform any or all of the functionsdescribed herein as being performed by a simulation model generatingapparatus will now be discussed below. For example, the storage unit 256may store a program including executable instructions corresponding toany or all of the operations described herein as being performed by asimulation model generating apparatus. According to at least one exampleembodiment, additionally or alternatively to being stored in the storageunit 256, the executable instructions may be stored in acomputer-readable medium including, for example, an optical disc, flashdrive, SD card, etc., and the simulation model generating apparatus 200may include hardware for reading data stored on the computerreadable-medium. Further, the processing unit 258 may be a processorconfigured to perform any or all of the operations described herein asbeing performed by a simulation model generating apparatus 200 and/orany or all functions described below with reference to FIGS. 2-8, forexample, by reading and executing the executable instructions stored inat least one of the storage unit 256 and a computer readable storagemedium loaded into hardware included in the simulation model generatingapparatus 200 for reading computer-readable mediums.

The term ‘processor,’ as used in the present disclosure, may refer to,for example, a hardware-implemented data processing device havingcircuitry that is physically structured to execute desired operationsincluding, for example, operations represented as code and/orinstructions included in a program. Examples of the above-referencedhardware-implemented data processing device include, but are not limitedto, a microprocessor, a central processing unit (CPU), a processor core,a multi-core processor, a multiprocessor, an application-specificintegrated circuit (ASIC), and a field programmable gate array (FPGA).Processors executing program code are programmed processors, and thus,are special-purpose computers

Examples of the simulation model generating apparatus 200 beingprogrammed, in terms of hardware, to perform any or all of the functionsdescribed herein as being performed by a simulation model generatingapparatus will now be discussed below. Additionally or alternatively toexecutable instructions corresponding to the functions described hereinas being performed by a simulation model generating apparatus beingstored in a storage unit or a computer-readable medium as is discussedabove, the processing unit 258 may include a circuit that has astructural design dedicated to performing any or all of the operationsdescribed herein as being performed by a simulation model generatingapparatus and/or any or all functions described below with reference toFIGS. 2-8. For example, the above-referenced circuit included in theprocessing unit 258 may be a FPGA or ASIC physically programmed, throughspecific circuit design, to perform any or all of the operationsdescribed herein as being performed by a simulation model generatingapparatus.

FIG. 2 is a flow chart illustrating an example of a simulation modelgenerating method according to at least some example embodiments.

Referring to FIG. 2, in operation S205, an XML file corresponding to aPID of a system is received. For example, in operation S205, thesimulation model generating apparatus 200 may receive an XML filecorresponding to a PID of a system. For example, if the system beingmodeled by the simulation model generating apparatus is a system of aprocess plant (e.g., a power plant or chemical processing plant) the XMLfile may be a file corresponding to a PID of a process plant. Accordingto at least some example embodiments, PID generating software used tocreate or access the PID of the system may export the PID of the systemin the form of the XML file received by the simulation model generatingapparatus 200 in operation S205. According to at least some exampleembodiments, the exported XML file follows PID XML Standard ISO 15926.An example of a PID and XML data corresponding to a PID will now bediscussed below with reference to FIGS. 3 and 4.

FIG. 3 illustrates an example of a portion of a PID 300. The portion ofthe PID 300 illustrated in FIG. 3 may be a portion of a single page ofthe PID 300. The PID 300 may span several pages. The PID 300 illustratedin FIG. 3 is a PID describing a system or systems of a nuclear powerplant. However, a PID describing a system or systems of a nuclear powerplant is used only as an example. PIDs can be generated for severaldifferent types of systems, and the PID to which the XML file receivedin operation S205 is not limited to being a PID that describes systemsassociated with nuclear power plants.

As is shown in FIG. 3, a PID can include visual depictions of severaldifferent types of components included in the system or systems beingillustrated by the PID. As is also shown in FIG. 3, different types ofcomponents may be illustrated using different types of symbols known tothose of ordinary skill in the subject matter area of the system orsystems illustrated in the PID. For example, the symbols used in a PIDlike that shown in FIG. 3 are defined in a legend and used consistentlyacross multiple diagrams. For example, the symbols illustrated in PID300 are recognizable to those familiar with PIDs for nuclear power plantdesigns. Examples of components within the portion of the PID 300illustrated in FIG. 3 include valves 305, a pressure instrument 311, aVenturi/orifice 315, a temperature instrument 319, filters 321, an offpage connector 323 and a differential pressure instrument 325. Valves305 are used for isolating/controlling flow in the system described bythe PID 300. The differential pressure instrument 325 and temperatureinstrument are used for measuring pressure and temperature,respectively, in the system described by the PID 300. TheVenturi/orifice 315 creates a decrease in area for measuringdifferential pressure to measure flow in the system described by the PID300. The filters 321 remove particles in from liquid in the systemdescribed by the PID 300. The off page connectors 323 each designate andlabel a system connection to another page of the PID 300. In the exampleshown in FIG. 3, that off page connectors 323 connect the portion of thePID 300 illustrated in FIG. 3 to clean water 954 and a makeup watersystem 951. The differential pressure instrument 325 measures adifference in pressure between two points in the system described by thePID 300. Further examples of components that could be included in thePID 300 include, but are not limited to, tanks and/or vessels, andsilencers. The tanks and/or vessels can be used, for example, forstoring mass and/or providing make up water to the system described bythe PID 300. The silencers can be used, for example to createrestrictions to flow or to remove turbulence. As is also shown in FIG.3, interconnections between the several different types of componentscan also be included in a PID. For example, the interconnectionsillustrated in the PID 300 may represent, for example, piping in betweenvarious components of a system or systems of a nuclear power plant. Asis noted above, a PID can be exported in the form of an XML file. Anexcerpt from such an XML file is illustrated in FIG. 4.

FIG. 4 illustrates a portion of an XML file 400. The XML file 400corresponds to the PID 300. As is illustrated in FIG. 4, the XML file400 includes XML data, i.e., data expressed using XML syntax. The XMLfile 400 follows the PID XML Standard ISO 15926. The portion of XML file400 shown in FIG. 4 illustrates XML data describing the filter componentFilter-0121, which is one of the filters 321 illustrated in the PID 300of FIG. 3. The filter component Filter-0121 is also referred to, in thepresent disclosure, simply as “the Filter-0121 component.” TheFilter-0121 component could be either one of the two filters 321illustrated in FIG. 3. The Filter-0121 component is represented in theXML file 400 as the “Equipment” element illustrated in FIG. 3B (i.e.,the XML element named “Equipment” illustrated in FIG. 4). Theillustrated “Equipment” element includes “ComponentName,”“ComponentClass,” “ID,” and “TagName” attributes, each of whichcorrespond to the component being described by the “Equipment” elementwhich, in the example illustrated in FIG. 4, is the Filter-0121component. The ComponentName attribute indicates that a component typeof the Filter-0121 component is a filter. The ComponentClass attributeindicates a class of components to which the Filter-0121 componentbelongs. According to at least some example embodiments, the TagNameattribute indicates a tag (i.e., “Filter-0121”) which may be illustratedin the PID 300 as a visual identifier of the Filter-0121 component.However, for the ease of description, the filters 321 are illustrated inthe PID 300 of FIG. 3 using only reference numerals, and not tag names.The ID attribute indicates an identifier value for the Filter-0121component described by the “Equipment” element illustrated in FIG. 4.According to at least some example embodiments, the identifier value ofthe ID attribute may uniquely identify, with respect to all componentsdescribed in the XML file 400 and/or included in the PID 300, theFilter-0121 component described by the “Equipment” element illustratedin FIG. 4. For example, even in a case where the TagName “Filter-0121”may be used for more than one filter described in the XML file 400and/or included in the PID to which the XML file 400 corresponds, theidentifier value of the ID attribute of the “Equipment” elementillustrated in FIG. 4 must be unique to the particular instance of theFilter-0121 component described by the “Equipment” element illustratedin FIG. 4. The unique ID attribute identifies the component to which theID attribute corresponds differentiates the identified component fromsimilar components in design documents (e.g., the PID) and thesimulation model.

The illustrated “Equipment” element of the XML file 400 of FIG. 4includes several sub-elements which may also be referred to as childelements. These sub-elements describe additional features of the filtercomponent described by the “Equipment” element. The addition featuresinclude, for example, a position of the filter component within the PIDto which the XML file 400 corresponds, an extent of the filter componentwithin the PID to which the XML file 400 corresponds (e.g., maximum andminimum horizontal positions and maximum and minimum vertical positionsof the filter component within the PID to which the XML file 400corresponds), and lines and colors included in the filter componentwithin the PID to which the XML file 400 corresponds. The sub-elementsalso include descriptions of several nozzles included in the filtercomponent.

Though, for the purpose of simplicity, FIG. 4 illustrates only XML datacorresponding to a single filter component, the XML file 400 may includeXML data describing any or all components included in the PID to whichthe XML file 400 corresponds. Further, the items described by the XMLdata included in the XML file 400 may be of several different types.Because, as is noted above, the XML file 400 is an example of an XMLfile exported from a PID that illustrates a system or systems of anuclear power plant, examples of the different types of components thatmay be described in the XML file 400 include, but are not limited to,pumps, valves, filters, tanks, piping segments, measuringinstrumentation, silencers, and page connectors. The page connectorsdepict connections that span adjacent pages of a multi-page PID.

Further, as is known, the specific types of attributes and/orsub-elements included in an element or sub-element of the XML file 400may vary depending on the type of component being described by theelement or sub-element of the XML file 400. For example, because the“Equipment” element illustrated in FIG. 4 describes the Filter-0121component, the types of attributes and/or sub-elements include the“Equipment” element illustrated in FIG. 4 correspond to filters.Consequently, elements or sub-elements of the XML file 400 that describecomponents other than filters may include types of attributes and/orsub-elements that differ from the types of attributes and sub-elementsin the “Equipment” element illustrated in FIG. 4.

The PID 300 and XML file 400 are generated using P&ID (computer-aideddesign) CAD software. The example of the PID 300 depicted in FIG. 3 isan example of a PID generated using SmartPlant® P&ID software, and theexample of the portion of XML file 400 depicted in FIG. 4 is an exampleof a portion of an XML file generated using SmartPlant® P&ID software.However, SmartPlant® P&ID software is just one example among severalknown types/brands of P&ID CAD software which may be used to generatePIDs and XML files for use with the simulation model generating methodillustrated in FIG. 2. For example, according to at least some exampleembodiments, the XML file retrieved in operation S205 of FIG. 2 and thePID to which the retrieved XML file corresponds can both be generated byany P&ID CAD software capable of generating XML data in accordance withthe PID XML Standard ISO 15926.

Returning to FIG. 2, in operation S210, objects (i.e., components)defined by the XML file are identified. For example, according to atleast some example embodiments, in operation S210, the simulation modelgenerating apparatus 200 may identify components defined by the XML filethat was received by the simulation model generating apparatus 200 inoperation S205. As is noted above with reference to FIG. 4, an XML filecorresponding to a PID may include XML data describing any or all ofcomponents, and interconnections between components, illustrated in thePID to which the XML file corresponds. In operation S210, the simulationmodel generating apparatus 200 may read the XML data included in an XMLfile that was exported from a PID file, and identify the variouscomponents described by the XML file. For example, the simulation modelgenerating apparatus 200 may read the XML file and identify thecomponents described by the XML file based on the attribute informationincluded in the elements and/or sub-elements included in the XML file.Using the structure of the “Equipment” element of the XML file 400illustrated in FIG. 4 as an example, in operation S210, the simulationmodel generating apparatus 200 may determine a type of a componentdescribed by an element included in the XML file 400 by reading the“ComponentName” attribute of the element, determine a name or tag of thecomponent described by the element included in the XML file 400 byreading, for example, the “TagName” or “ItemTag” attribute of theelement, and determine an identifier value of a component described byan element included in the XML file 400 by reading the “ID” attribute ofthe element. According to at least some example embodiments, the XMLfile may also specify performance data of the components included in theXML file 400, e.g. flowrate, flow area, heat transfer area, length,filter efficiency, which is needed for the simulation platform.Alternately, the performance information may be read from a separatefile. Further, though an XML file is used as an example of a file inwhich the above-referenced performance data may be stored, theperformance data can be stored in formats other than XML.

In operation S215, information describing the identified components isstored, based on the XML file. For example, in operation S215, thesimulation model generating apparatus 200 may store informationdescribing the components that were identified by the simulation modelgenerating apparatus 200 in operation S210. The simulation modelgenerating apparatus 200 may extract information describing theidentified components from the XML file that was received by thesimulation model generating apparatus 200 in operation S205, and storethe extracted data, for example, in the storage unit 256. According toat least some example embodiments, for each component the simulationmodel generating apparatus 200 identified in operation S210, inoperation S215, the simulation model generating apparatus 200 may createan array corresponding to the component, populate the array withinformation corresponding to the attributes and/or sub-elements of theelement or sub-element describing the component in the XML file, andstore the array. For example, an example component array thatcorresponds to the Filter-0121 component described by the “Equipment”element illustrated in FIG. 4 and may be created by the simulation modelgenerating apparatus 200 in operation S215 is illustrated in Table 1,below.

TABLE 1 Component Array Element Type Component Array Element Value IDSP70A6483926D04E4F897179BD3F2BA36C Component Filter Name TagNameFilter-0121 PosX [X coordinate of the position of the Filter-0121component] PosY [Y coordinate of the position of the Filter-0121component] NozID SP4E731C905AAC4730A06B831EA7A51B2E NozName FlangedNozzle NozPosX [X coordinate of the position of nozzle “SP58...”]NozPosY [Y coordinate of the position of nozzle “SP58...”] NozIDSPAE7F9B675581476BB501A28F619C9D26 PMinX [minimum X coordinate of theFilter-0121 component] PMinY [minimum Y coordinate of the Filter-0121component] PMaxX [maximum X coordinate of the Filter-0121 component]PMaxY [maximum Y coordinate of the Filter-0121 component]

As is illustrated in Table 1, the array corresponding to the Filter-0121component may include, as a value of an “ID” array element, the value ofthe “ID” attribute extracted by the simulation model generatingapparatus 200 from the “Equipment” element of the XML file 400 thatdescribes the Filter-0121 component. The array illustrated in Table 1that corresponds to the Filter-0121 component may include, as a value ofa “Name” array element, the value of the “ComponentName” attributeextracted by the simulation model generating apparatus 200 from the“Equipment” element of the XML file 400 that describes the Filter-0121component. The array illustrated in Table 1 that corresponds to theFilter-0121 component may include, as a value of a “TagName” arrayelement, the value of the “TagName” attribute extracted by thesimulation model generating apparatus 200 from the “Equipment” elementof the XML file 400 that describes the Filter-0121 component. The arrayillustrated in Table 1 that corresponds to the Filter-0121 component mayinclude, as values of “PosX” and “Posy” array elements, respectively,“X” and “Y” values of the “Position” sub-element extracted by thesimulation model generating apparatus 200. The array illustrated inTable 1 that corresponds to the Filter-0121 component may include, as 4different “NozID” array elements, the values of the 4 “ID” attributesextracted by the simulation model generating apparatus 200,respectively, from the 4 different “Nozzle” sub-elements of the“Equipment” element of the XML file 400 that describes the Filter-0121component. Further, the array illustrated in Table 1 that corresponds tothe Filter-0121 component may include, for each “NozID” array element,corresponding “NozName,” “NozPosX,” and “NozPosY” array elements. As isillustrated in Table 1, the simulation model generating apparatus 200may group the “NozName,” “NozPosX,” and “NozPosY” array elements withthe “NozID” array element to which the “NozName,” “NozPosX,” and“NozPosY” array elements correspond. The simulation model generatingapparatus 200 may extract, as the value of the “NozName” array elementof the array illustrated in Table 1, the “ComponentName” attribute ofthe corresponding one of the 4 “Nozzle” sub-elements of the “Equipment”element of the XML file 400 that describes the Filter-0121 component.The simulation model generating apparatus 200 may extract, as the valuesof the “NozPosX” and “NozPosY” array elements of the array illustratedin Table 1, respectively, “X” and “Y” values of a “Position” sub-elementof the corresponding one of the 4 “Nozzle” sub-elements of the“Equipment” element of the XML file 400 that describes the Filter-0121component. The simulation model generating apparatus may extract, as the“PMinX” array element of the array illustrated in Table 1, an “X”attribute of a “Min” sub-element of the “Extent” sub-element of the“Equipment” element of the XML file 400 that describes the Filter-0121component. The simulation model generating apparatus may extract, as the“PMinY” array element of the array illustrated in Table 1, a “Y”attribute of a “Min” sub-element of the “Extent” sub-element of the“Equipment” element of the XML file 400 that describes the Filter-0121component. The simulation model generating apparatus may extract, as the“PMaxX” array element of the array illustrated in Table 1, an “X”attribute of a “Max” sub-element of the “Extent” sub-element of the“Equipment” element of the XML file 400 that describes the Filter-0121component. The simulation model generating apparatus may extract, as the“PMaxY” array element of the array illustrated in Table 1, a “Y”attribute of the “Max” sub-element of the “Extent” sub-element of the“Equipment” element of the XML file 400 that describes the Filter-0121component.

Table 1, above, is provided as an example of an array that includesattributes of a component listed in an XML file. However, an arraycreated for a component described in an XML file is not limited toincluding only the information shown in Table 1. Additional types ofinformation that may be included in the array shown in Table 1 include,but are not limited to, identification of graphical elements of thecomponent corresponding to the array, topology information about thecomponent corresponding to the array, and information about dimensionsof the component corresponding to the array (e.g., pipe diameters).

Further, table 1, above, is provided as an example of a component arraycreated for a filter component described by XML file 400. Accordingly,the contents of the component array shown in Table 1 correspond toattributes of a filter component. Those skilled in the art willunderstand that component arrays created for components other thanfilter components (e.g., page connector, piping segment, tank, valve,check valve, and/or pump components) may include types of attributesthat correspond to attributes of the type of component for which thecomponent array is created, and may differ from at least some of thetypes of attributes included in Table 1.

Table 1 is discussed above with reference to an example in which thecontents of Table 1 are stored in an array data structure. However,according to at least some example embodiments, instead of, or inaddition to, storing the contents of Table 1 in an array data structure,the contents of Table 1 may also be stored in an object data structurethat includes elements corresponding to each of the elements discussedabove as being included in Table 1.

In addition to the topology and arrangement of components otherinformation can be provided in the ISO file. For example the diameter ofpipes is exported to the XML file, and this can be loaded into thesimulation model to characterize the hydraulic resistance of the flowpaths.

3D CAD models are also typically available when the simulation model iscreated. Exporting piping data from a 3D CAD model correlated with theEquipmentlD or “ID” (which uniquely identifies each component) canfacilitate identification of the lengths of flow paths, and elevationdifferences between components, in a simulation hydraulic model. The 3Dmodel can also identify elbows, and tee's in the piping whose flowresistance coefficient can be determined using correlations such asIdelchik or the Crane handbook.

SW tools used to produce the P&ID often are used to load in a databaseadditional design information which is needed to procure the equipment.Database reports from the design tool indexed by EquipmentlD or “ID”(which uniquely identifies each component) can be reformatted andimported into most simulation tools, once the topology and arrangementof components is defined through this process. Examples of the type ofinformation available are pump rated head and flowrate, heat exchangerheat transfer area, flow area and hydraulic diameter and valve losscharacteristic as a function of open fraction.

Thus, the simulation model generating method and apparatus according toat least some example embodiments, provide the ability correlate andtransfer data, and thus, provide the ability to automate the developmentof most of the simulation model.

The values of the “ID” array element and “NozID” array elements of thearray shown in Table 1 that corresponds to the Filter-0121 component areillustrated as the unique identification values read from the “ID”attributes of the “Equipment” element and nozzle sub elements thatdescribe the Filter-0121 component within the XML file 400. However,according to at least one example embodiment, when generating the arrayshown in Table 1 in operation S215, the simulation model generatingapparatus 200 may assign a different 4-digit value (e.g., “0001”) toeach of several different unique identification value read from an “ID”attribute of an element or sub-element. For example, the simulationmodel generating apparatus 200 may start with the 4-digit value “0001”and increment the 4-digit value, for example, by 1, for every new uniqueidentification value corresponding to every ID array element of everycomponent array generated by the simulation model generating apparatus200.

For example, in a scenario where the array illustrated in Table 1 is thefirst array generated by the simulation model generating apparatus 200,the simulation model generating apparatus 200 may start by assigning the4-digit value “0001” to the “ID” attribute of the “Equipment” elementillustrated in FIG. 4. Further, the simulation model generatingapparatus 200 may sequentially assign the values “0002,” “0003,” “0004,”and “0005” to the 4 unique identifier values read from the 4 “ID”attributes of the 4 “Nozzle” sub-elements of the “Equipment” elementillustrated in FIG. 4. When the simulation model generating apparatusgenerates the arrays (e.g., the array shown in Table 1) in operationS215, the simulation model generating apparatus 200 may use the 4-digitvalues as values of array elements in place of the unique identifiervalues to which the 4-digit values are assigned.

Further, in operation S215, the simulation model generating apparatus200 may also store a correspondence table defining the correspondencebetween the unique identifier value stored in the “ID” attribute or anelement or sub-element, and the 4-digit value generated the simulationmodel generating apparatus 200 that corresponds to the uniqueidentifier. Thus, according to at least some example embodiments, thesimulation model generating apparatus 200 can check the correspondencetable to see if a 4-digit value has already been assigned to a uniqueidentifier, and avoid generating a new 4-digit value for uniqueidentifiers to which the simulation model generating apparatus 200 hasalready assigned a 4-digit value. Though 4-digit values are discussedabove as an example, the operations described above with respect to the4-digit values may be applied to any desired number of digits including,for example, 3-digit values, 5-digits values and 6-digit values.

According to at least some example embodiments, in operation S215, thesimulation model generating apparatus 200 adds each of the generatedarrays to at least one of a plurality of array lists, and stores thearray lists, for example, in storage unit 256. Examples of differenttypes of array lists will be discussed in greater detail below withreference to FIG. 5.

Though operations S210 and S215 are illustrated as separate steps,according to at least some example embodiments, the simulation modelgenerating apparatus 200 may perform operations S210 and S215 as asingle step or separate steps.

Returning to FIG. 2, in operation S220, a simulation model is generatedbased on the information describing the identified components. Forexample, in operation S220, the simulation model generating apparatus200 may generate a simulation model based on the information describingthe identified components that was stored by the simulation modelgenerating apparatus 200 in operation S215.

According to at least some example embodiments, in operation S220, thesimulation model generating apparatus 200 creates a simulation modelfile corresponding to a desired simulation modeling softwareenvironment. The desired simulation modeling software environment may bechosen, for example, in accordance with the preference of a simulationengineer or user performing a method in accordance with any of FIGS.2-8. Further, the simulation model generating apparatus 200 reads thearrays that were created and stored by the simulation model generatingapparatus 200 in operation 215. Further, for each array read, thesimulation model generating apparatus 200 may generate a correspondingdescription of a component using the syntax of the desired simulationmodeling software environment, and add the description to the simulationmodel file. The resulting simulation model file may define a simulationmodel.

Consequently, in operation S220, the simulation model generatingapparatus 200 generates a simulation model by building the generationmodel file in the manner discussed above. Further, the simulation modelgenerated in operation S220 may then be used by the simulation modelgenerating apparatus 200 or a different apparatus to perform varioustypes of simulations within the desired simulation modeling softwareenvironment. Further, the simulation model generated in operation S220may correspond or substantially correspond to the PID that was exportedas the XML file received in operation S205, without the need for asimulation engineer to create the simulation model by manually entering,into the simulation model, each component and interconnection includedin the PID. Consequently, an amount of time associated with creating asimulation model that corresponds to a PID may be decreasedsignificantly.

More detailed explanations of operations S210˜S220, according to atleast some example embodiments, are discussed below with respect toFIGS. 5-7.

FIG. 5 illustrates a method of performing object (i.e., component)identification according to at least some example embodiments. Accordingto at least some example embodiments, operation S210 may be performed inaccordance with FIG. 5. According to at least some example embodiments,operations S210 and S215 may be performed in accordance with FIG. 5.

FIGS. 5-7 will be described with reference to a scenario in which (i)the XML file received in operation S205 represents piping segments ascomponents, and (ii) according to the syntax of the simulation modelfile generated in step S220, piping segments are represented as linksthat originate at a first node and terminate at a second node, and eachlink may be a pump link or a flow link. An example of theabove-referenced scenario includes an operation of the simulation modelgenerating apparatus 200 generating a simulation model file using thesyntax of a simulation platform simulation model based on an XML fileexported from a PID by SmartPlant® P&ID software. Examples of differentsimulation platforms this apparatus applies to include Modelica,MATLAB™, 3KEYMASTER™, JADE™. In accordance with the syntax of a3KEYMASTER™ simulation platform simulation model, some components (e.g.,tanks, filters, valves, check valves, and page connectors) are definedas nodes, and some components (e.g., pipe segments and pumps) aredefined as links. Accordingly, with respect to the description of FIGS.5-7 below, arrays generated by the simulation model generating apparatus200 for nodes may be referred to as node arrays, and arrays generated bythe simulation model generating apparatus 200 for links may be referredto as link arrays.

However, according to at least some example embodiments, the simulationmodel generating apparatus 200 is not limited to generating simulationmodels that have the syntax of a specific simulation platform simulationmodel, and the simulation model generating apparatus 200 is not limitedto using XML files that are exported from PIDs by a specific P&ID CADsoftware.

Referring to FIG. 5, in operation S502 an object (i.e., component)identification operation is initiated for a component included in theXML file received in operation S205 of FIG. 2. For example, in operationS502, the simulation model generating apparatus 200 may read an elementor sub-element defining a component from the XML file received inoperation S205 of FIG. 2.

In operation S505, the simulation model generating apparatus 200determines whether the component defined by the element or sub-elementread in operation S502 is a page connector. For example, according to atleast some example embodiments, in operation S505, the simulation modelgenerating apparatus 200 may determine whether the component defined bythe element or sub-element read in operation S502 is a page connector bydetermining whether a “ComponentName” attribute of the component definedby the element or sub-element read in operation S502 has a valuecorresponding to a page connector component.

If the simulation model generating apparatus 200 determines, inoperation S505, that the component defined by the element or sub-elementread in operation S502 is a page connector, the simulation modelgenerating apparatus 200 proceeds to operation S510.

In operation S510, the simulation model generating apparatus 200extracts information defining the page connector component from the XMLfile received in operation S205 of FIG. 2, and stores the extractedinformation. For example, the simulation model generating apparatus 200may generate an array corresponding to the page connector component inthe same manner discussed above with respect to operation S215 of FIG. 2and the array illustrated in Table 1. For example, the array generatedfor the page connector component may include array elements for at leastposition information, component name information, and ID information ofthe page connector component. Further, in operation S510, the simulationmodel generating apparatus 200 may store the array corresponding to thepage connector component in one of a plurality of array lists.

According to at least one example embodiment, the simulation modelgenerating apparatus 200 may create an on-link node array list, anendpoint node array list, and a link array list. The on-link node arraylist may store arrays corresponding to components that are defined asnodes that are placed on top of links in accordance with the designrules of the desired simulation modeling software environment. Examplesof types of components that correspond to the arrays included in theon-link node array list in accordance with the design rules of somesimulation platforms (e.g., 3KEYMASTER™) include, for example, valvecomponents and check valve components. The endpoint node array list maystore arrays corresponding to components that can act as origin ortermination nodes of a link in accordance with the design rules of thedesired simulation modeling software environment. Examples of types ofcomponents that correspond to the arrays included in the endpoint nodearray list in accordance with the design rules of some simulationplatforms (e.g., 3KEYMASTER™) include, for example, tank components andfilter components. The link array list may store arrays corresponding tocomponents that are defined as links in accordance with the design rulesof the desired simulation modeling software environment. Examples oftypes of components that correspond to arrays included in the link arraylist in accordance with the design rules of some simulation platforms(e.g., 3KEYMASTER™) include, for example, pump components and pipingsegment components. Alternatively, the simulation platform may use adifferent scheme of simulating fluid systems, including, for example, ascheme in which, instead of pumps being defined as a link between nodes,a pump would be a component that would be between two nodes. Further, avalve or check valve could also be simulated in a different manner. Forexample, instead of the valve or check valve being placed on a flowlink, the valve or check valve could be a component that is connectedfrom one portion of the flow link to another portion of the flow link,or connected between 2 flow links.

If the simulation model generating apparatus 200 determines, inoperation S505, that the component defined by the element or sub-elementread in operation S502 is not a page connector, the simulation modelgenerating apparatus 200 proceeds to operation S515.

In operation S515, the simulation model generating apparatus 200determines whether the component defined by the element or sub-elementread in operation S502 is a piping segment. For example, according to atleast some example embodiments, in operation S515, the simulation modelgenerating apparatus 200 may determine whether the component defined bythe element or sub-element read in operation S502 is a piping segment bydetermining whether a “ComponentName” attribute of the component definedby the element or sub-element read in operation S502 has a valuecorresponding to a piping segment component.

If the simulation model generating apparatus 200 determines, inoperation S515, that the component defined by the element or sub-elementread in operation S502 is a piping segment, the simulation modelgenerating apparatus 200 proceeds to operation S520.

In operation S520, the simulation model generating apparatus 200determines whether the piping segment splits (e.g., branches).

If, in operation S520, the simulation model generating apparatus 200determines that the piping segment splits, the simulation modelgenerating apparatus 200 proceeds to operation S525.

In operation S525, the simulation model generating apparatus 200 maygenerate and store multiple arrays defining multiple links. For example,if a piping segment originates at a first node and branches into twopipes that connect to second and third nodes, respectively, thesimulation model generating apparatus 200 may generate and store a nodearray corresponding to a new fourth node located at the point where thetwo pipes split. The simulation model generating apparatus 200 maygenerate and store a first link array defining a first link asoriginating at the first node and terminating at the new fourth node.The simulation model generating apparatus 200 may generate and store asecond link array defining a second link as originating at the newfourth node and terminating at the second node. Further, the simulationmodel generating apparatus 200 may generate and store a third link arraydefining a third link as originating at the new fourth node andterminating at the third node.

In operation S530, the simulation model generating apparatus 200 mayextract node name and/or ID value and node position values from the XMLfile received in operation S205 of FIG. 2, and populate array elementsof the first, second and third link arrays generated in operation S525with corresponding node name and/or ID values and node position values.For example, the element or sub-element in the XML file that defines thepiping segment component identified by the simulation modeling apparatusin operation S515 may also include, for example, a “FromID” valueidentifying an origin node of the piping segment and one or more “ToID”values identifying one or more termination nodes of the piping segment.The “FromID” and “ToID” values may be, for example, attributes of a“Connection” sub-element of a “PipingNetworkSegment” element of the XMLfile that defines the piping segment identified in operation S515.Accordingly, in operation S530, the simulation model generatingapparatus 200 can create or populate array elements that specify linkorigin nodes and link termination nodes for each of the first, secondand third link arrays. According to at least some example embodiments,each of the first, second and third nodes may be, for example,components for which arrays have already been generated by thesimulation model generating apparatus 200. Accordingly, the simulationmodel generating apparatus 200 may refer to the arrays corresponding tothe first, second and third nodes in order to acquire the positioninformation of the first, second and third nodes that may be included asvalues for position array elements of the first, second and third linkarrays. According to at least some example embodiments, the simulationmodel generating apparatus 200 placed node arrays corresponding to thefirst, second and third nodes in the endpoint node array list, forexample, when the simulation model generating apparatus 200 created thearrays corresponding to the first, second and third nodes.

According to at least some example embodiments, in operation S530, thesimulation model generating apparatus 200 may store the first, second,and third link arrays in the link array list, and may store the nodearray defining the new fourth node in the endpoint node array list.

If, in operation S520, the simulation model generating apparatus 200determines that the piping segment does not split, the simulation modelgenerating apparatus 200 proceeds to operation S535.

In operation S535, the simulation model generating apparatus 200 maygenerate and store a link array defining a link corresponding to thepiping segment identified by the simulation model generating apparatus200 in operation S515.

In operation S540, the simulation model generating apparatus 200 mayextract node name and/or ID value and node position values from the XMLfile received in operation S205 of FIG. 2, and populate array elementsof the link array generated in operation S535 using, for example, a“FromID” value identifying an origin node of the piping segment and a“ToID” values identifying one or more termination nodes of the pipingsegment. The “FromID” and “ToID” values may be, for example, attributesof a “Connection” sub-element of a “PipingNetworkSegment” element of theXML file that defines the piping segment identified in operation S515.

In accordance with the design rules of the simulation platform, therecan be different types of links including, for example, flow links andpump links. According to at least some example embodiments, pump linksmay differ from flow links in that a pump link describes a link to whicha pumping force is applied. According to at least some exampleembodiments, each of the links described above with respect tooperations S525-S540 may be a flow links. Examples of pump links aredescribed below with reference to steps S580 an S585.

If the simulation model generating apparatus 200 determines, inoperation S515, that the component defined by the element or sub-elementread in operation S502 is not a piping segment, the simulation modelgenerating apparatus 200 proceeds to operation S520.

In operation S545, the simulation model generating apparatus 200determines whether the component defined by the element or sub-elementread in operation S502 is a tank. For example, according to at leastsome example embodiments, in operation S545, the simulation modelgenerating apparatus 200 may determine whether the component defined bythe element or sub-element read in operation S502 is a tank bydetermining whether a “ComponentName” attribute of the component definedby the element or sub-element read in operation S502 has a valuecorresponding to a tank component.

If the simulation model generating apparatus 200 determines, inoperation S545, that the component defined by the element or sub-element(of Component Class or Component Name) read in operation S502 is a tank,(or accumulator, drum or vessel) the simulation model generatingapparatus 200 proceeds to operation S550.

In operation S550, the simulation model generating apparatus 200generates and stores a node array corresponding to the tank componentidentified in operation S545.

In operation S555, the simulation model generating apparatus 200extracts information defining the tank component from the XML filereceived in operation S205 of FIG. 2, and stores the extractedinformation in the node array generated in operation S550. For example,the simulation model generating apparatus 200 may generate an arraycorresponding to the tank component in the same manner discussed abovewith respect to operation S215 of FIG. 2 and the array illustrated inTable 1. For example, the array generated for the tank component mayinclude array elements for at least position information, component nameinformation, and ID information of the tank component. Further, inoperation S555, the simulation model generating apparatus 200 may storethe array corresponding to the tank component in the endpoint node arraylist.

If the simulation model generating apparatus 200 determines, inoperation S545, that the component defined by the element or sub-elementread in operation S502 is not a tank component, the simulation modelgenerating apparatus 200 proceeds to operation S560.

In operation S560, the simulation model generating apparatus 200determines whether the component defined by the element or sub-elementread in operation S502 is a valve. For example, according to at leastsome example embodiments, in operation S545, the simulation modelgenerating apparatus 200 may determine whether the component defined bythe element or sub-element read in operation S502 is a valve bydetermining whether a “ComponentName” attribute of the component definedby the element or sub-element read in operation S502 has a valuecorresponding to a valve component.

If the simulation model generating apparatus 200 determines, inoperation S560, that the component defined by the element or sub-elementread in operation S502 is a valve, the simulation model generatingapparatus 200 proceeds to operation S565.

In operation S565, the simulation model generating apparatus 200generates and stores a node array corresponding to the valve componentidentified in operation S560.

In operation S570, the simulation model generating apparatus 200extracts information defining the valve component from the XML filereceived in operation S205 of FIG. 2, and stores the extractedinformation in the node array generated in operation S565. For example,the simulation model generating apparatus 200 may generate a node arraycorresponding to the valve component in the same manner discussed abovewith respect to operation S215 of FIG. 2 and the array illustrated inTable 1. For example, the array generated for the valve component mayinclude array elements for at least position information, component nameinformation, and ID information of the valve component. Additionally,for valves (as well as check valves and other on-link type components),the generated node array may further include information extracted fromthe XML file 400 that identifies connection points of the valve or othercomponents to which the valve is connected (e.g., “FromID” and “ToID”attributes). Further, in operation S570, the simulation model generatingapparatus 200 may store the node array corresponding to the valvecomponent in the on-link node array list.

If the simulation model generating apparatus 200 determines, inoperation S560, that the component defined by the element or sub-elementread in operation S502 is not a valve component, the simulation modelgenerating apparatus 200 proceeds to operation S575.

In operation S575, the simulation model generating apparatus 200determines whether the component defined by the element or sub-elementread in operation S502 is a pump. For example, according to at leastsome example embodiments, in operation S575, the simulation modelgenerating apparatus 200 may determine whether the component defined bythe element or sub-element read in operation S502 is a pump bydetermining whether a “ComponentName” or “Name” attribute of thecomponent defined by the element or sub-element read in operation S502has a value corresponding to a pump component.

If the simulation model generating apparatus 200 determines, inoperation S575, that the component defined by the element or sub-elementread in operation S502 is a pump, the simulation model generatingapparatus 200 proceeds to operation S580.

In operation S580, the simulation model generating apparatus 200generates and stores a link array corresponding to the pump componentidentified in operation S560.

In operation S585, the simulation model generating apparatus 200extracts information defining the pump component from the XML filereceived in operation S205 of FIG. 2, and stores the extractedinformation in the link array generated in operation S580. For example,the simulation model generating apparatus 200 may generate a link arraycorresponding to the pump component in the same manner discussed abovewith respect to operation S215 of FIG. 2 and the array illustrated inTable 1. For example, the link array generated for the pump componentmay include array elements for at least position information of the pumpcomponent, component name information of the pump component, and IDinformation of the pump component. Additionally, the link arraygenerated for the pump component may define a pump link. Further, inoperation S570, the simulation model generating apparatus 200 may storethe link array corresponding to the pump component in the link arraylist.

According to at least some example embodiments, in operation S585, thesimulation model generating apparatus 200 may store the link arraygenerated in operation S580 in the link array list.

Referring to FIG. 5, if the simulation model generating apparatus 200does not identify the component defined by the element or sub-elementread in operation S502, the simulation model generating apparatus 200may return to step S502, read a new element or sub-element from the XMLfile received in operation S205 of FIG. 2, and attempt to identify acomponent defined by the new element or sub-element in accordance withsteps S505-S585.

The various component types described with respect to FIG. 5 (e.g., pageconnector, piping segment, tank, valve, and pump) are provided asexamples. The simulation model generating apparatus 200 is not limitedto identifying the component defined by the element or sub-element readin operation S502 as one of the component types described with respectto FIG. 5. According to at least some example embodiments, thesimulation model generating apparatus 200 is further capable ofidentifying additional component types including, for example, filtercomponent types and check valve component types, which can be processedaccording to the methods described for tanks and valves, respectively.

FIGS. 6 and 7 are flow charts for illustrating a method of generating asimulation model file according to at least some example embodiments.FIG. 6 describes an example of a manner in which the node arraysgenerated in the object identification method described above withrespect to FIG. 5 are used to generate the simulation model file. FIG. 7describes an example of a manner in which the link arrays generated inthe method described above with respect to FIG. 5 are used to generatethe simulation model file.

Referring to FIG. 6, in operation S605, the simulation model generatingapparatus 200 may create a simulation model file in accordance with thefile format of the desired simulation modeling software environment, andidentify a numbers and positions of the components described by the nodearrays discussed above with respect to FIG. 5. Operation S605 mayinclude two sub-operations, S610 and S620.

In operation S610, the simulation model generating apparatus 200 mayread the information stored in node arrays listed in the endpoint nodelist discussed above with respect to FIG. 5. In operation S615, thesimulation model generating apparatus 200 may use the information readin operation S610 to generate descriptions of each of the componentscorresponding to the node arrays listed in the endpoint node list, usingthe syntax of the desired simulation modeling software environment. Thesimulation model generating apparatus 200 may add each of thedescriptions generated in operation S615 to the simulation model filecreated in operation S605, thereby defining, in the simulation modelfile, node objects using the syntax of the desired simulation modelingsoftware environment. Thus, according to at least some exampleembodiments, each node object defined in the simulation model file inoperation S615 may correspond to an endpoint node array included in theendpoint node array list described above with respect to FIG. 5.

As is illustrated in FIG. 6, according to at least some exampleembodiments, the node objects defined in the simulation model file bythe simulation model generating apparatus 200 in operation S615 may eachinclude an ID value “ID,” a position value “Pos,” a type value “Type,” aname value “Name,” and graphic information “BMP.”

According to at least some example embodiments, the node objects definedin the simulation model file by the simulation model generatingapparatus 200 in operation S615 may each include, as an identifier(e.g., “ID”) value, a unique 4-digit integer. Further, the unique4-digit integers included in the definitions of the node objects addedto the simulation model file in operation S615 may be the unique 4-digitintegers assigned to the components for which the endpoint node arrayscorresponding to the node objects were generated. Examples of generatingthe unique 4-digit integers for component arrays are discussed abovewith respect to Table 1. Similarly, component tag names included in thedefinitions of the node objects added to the simulation model file inoperation S615 may be or include the tag names of the components forwhich the endpoint node arrays corresponding to the node objects weregenerated.

In operation S615, for each node object being defined in the simulationmodel file, the simulation model generating apparatus 200 may determinethe position value “Pos” of the node object based on the positioninformation (e.g., coordinates) included in the endpoint node array towhich the node object corresponds, determine the type value “Type” ofthe node object based on the type information (e.g., type=tank or pageconnector) included in the endpoint node array to which the node objectcorresponds, determine the name value “Name” of the node object based onthe name information (e.g., a tag name) included in the endpoint nodearray to which the node object corresponds, and determine the graphicinformation “BMP” of the node by providing a link to an image file(e.g., a bitmap) that corresponds to the type information determined forthe node object.

According to at least some example embodiments, before performingoperation S620, the simulation model generating apparatus 200 mayproceed to the method illustrated in FIG. 7.

Referring to FIG. 7, in operation S705, the simulation model generatingapparatus 200 identifies links.

According to at least some example embodiments, operation S710 is asub-operation of operation S705. In operation S710, the simulation modelgenerating apparatus 200 may access link arrays that definecorresponding components by reading the link array list described abovewith respect to FIG. 5.

In step S715, the simulation model generating apparatus 200 may read theinformation stored in each of the link arrays listed in the link arraylist.

In operation S720, the simulation model generating apparatus 200 mayidentify “FromID” and “ToID” information included in the informationread from each of the link arrays in operation S715. In operation S725,based on the “FromID” and “ToID” information identified in operationS720, the simulation model generating apparatus 200 may determine, foreach link defined by a link array included in the link array list, thenodes that act as endpoints for the link, and may generate descriptionsof each of the links using the syntax of the desired simulation modelingsoftware environment. The simulation model generating apparatus 200 mayadd each of the descriptions generated in operation S725 to thesimulation model file created in operation S605, thereby defining, inthe simulation model file, link objects using the syntax of the desiredsimulation modeling software environment.

As is illustrated in FIG. 7, according to at least some exampleembodiments, the link objects defined in the simulation model file bythe simulation model generating apparatus 200 in operation S725 may eachinclude an ID value “ID,” a position value “Pos,” a type value “Type,” aname value “Name,” the “FromID” and “ToID” values, width and colorvalues Width and Color, a “NumOfPoints” information item and a “Points”information item.

According to at least some example embodiments, the node objects definedin the simulation model file by the simulation model generatingapparatus 200 in operation S725 may each include, as an identifier(e.g., “ID”) value, a unique 4-digit integer. Further, the unique4-digit integers included in the definitions of the link objects addedto the simulation model file in operation S725 may be the unique 4-digitintegers assigned to the components for which the link arrayscorresponding to the link objects were generated. Examples of generatingthe unique 4-digit integers for component arrays are discussed abovewith respect to Table 1. Similarly, component tag names included in thedefinitions of the link objects added to the simulation model file inoperation S725 may be or include the tag names of the components forwhich the link arrays corresponding to the link objects were generated.

In operation S720, for each link object being defined in the simulationmodel file, the simulation model generating apparatus 200 may determinethe position value “Pos” of the link object based on the positioninformation (e.g., coordinates) included in the link array to which thelink object corresponds, determine the type value “Type” of the linkobject based on the type information (e.g., type=pump link or flow link)included in the link array to which the link object corresponds,determine the name value “Name” of the link object based on the nameinformation (e.g., a tag name) included in the link array to which thelink object corresponds, determine the “FromID” and “ToID” values of thelink object based on FromID and ToID information (e.g., the FromID andToID information discussed above with reference to operation S535)included in the link array to which the link object corresponds, anddetermine the “Color” and “Width” values of the link object based oncolor and width information included in the link array to which the linkobject corresponds. Further, in operation S720, for each link objectbeing defined in the simulation model file, the simulation modelgenerating apparatus 200 may use the attribute information read from thelink arrays in operation S715 to generate the “NumOfPoints” item, whichcontains information items identifying a number of points through whichthe corresponding link will be routed, and generate the “Points” item,which contains information identifying coordinates of each of the pointsthrough which the corresponding link will be routed.

Thus, according to at least some example embodiments, each link objectdefined in the simulation model file in operation S725 may correspond toa link array included in the link array list described above withrespect to FIG. 5. According to at least some example embodiments, thelink objects defined in the simulation model file by the simulationmodel generating apparatus 200 in operation S725 may each include, as anidentifier (e.g., “ID”) value, a unique 4-digit integer. Further, theunique 4-digit integers included in the definitions of the link objectsin the simulation model file may be the unique 4-digit integers assignedto the components for which the link arrays corresponding to the linkobjects were generated. Examples of generating the unique 4-digitintegers for component arrays are discussed above with respect toTable 1. Similarly, component tag names included in the definitions ofthe link objects in the simulation model file may be or include the tagnames of the components for which the link arrays corresponding to thelink objects were generated.

Further, the link objects defined in the simulation model file by thesimulation model generating apparatus 200 in operation S725 canrepresent connections between 2 nodes and can each be either a pump linkor a flow link. The pump link is a link that adds energy (flow) to thesystem being modeled by the simulation modeling software environment. Aflow link passes energy in the system being modeled by the simulationmodeling software environment.

According to at least some example embodiments, after performingoperation S725, the simulation model generating apparatus 200 may returnto the method illustrated in FIG. 6.

Returning to FIG. 6, in operation S620, the simulation model generatingapparatus 200 may read the information stored in node arrays listed inthe on-link node list discussed above with respect to FIG. 5. Inoperation S625, the simulation model generating apparatus 200 may usethe information read in operation S620 to generate descriptions of eachof the node objects corresponding to the node arrays listed in theon-link node list, using the syntax of the desired simulation modelingsoftware environment. The simulation model generating apparatus 200 mayadd each of the descriptions generated in operation S625 to thesimulation model file created in operation S605, thereby defining, inthe simulation model file, node objects using the syntax of the desiredsimulation modeling software environment. Thus, according to at leastsome example embodiments, each node object defined in the simulationmodel file in operation S625 may correspond to an on-link node arrayincluded in the on-link node array list described above with respect toFIG. 5.

As is illustrated in FIG. 6, according to at least some exampleembodiments, the node objects defined in the simulation model file bythe simulation model generating apparatus 200 in operation S625 may eachinclude an ID value “ID,” a position value “Pos,” a paste ID value“PasteID,” a type value “Type,” a name value “Name,” and graphicinformation “BMP.”

According to at least some example embodiments, the node objects definedin the simulation model file by the simulation model generatingapparatus 200 in operation S625 may each include, as an identifier(e.g., “ID”) value, a unique 4-digit integer. Further, the unique4-digit integers included in the definitions of the node objects in thesimulation model file may be the unique 4-digit integers assigned to thecomponents for which the on-link node arrays corresponding to the nodeobjects were generated. Examples of generating the unique 4-digitintegers for component arrays are discussed above with respect toTable 1. Similarly, component tag names included in the definitions ofthe node objects added to the simulation model in operation S625 filemay be or include the tag names of the components for which the on-linknode arrays corresponding to the node objects were generated.

In operation S625, for each node object being defined in the simulationmodel file, the simulation model generating apparatus 200 may determinethe position value “Pos” of the node object based on the positioninformation (e.g., coordinates) included in the on-link node array towhich the node object corresponds, determine the type value “Type” ofthe node object based on the type information (e.g., type=valve or checkvalve) included in the on-link node array to which the node objectcorresponds, determine the name value “Name” of the node object based onthe name information (e.g., a tag name) included in the on-link nodearray to which the node object corresponds, and determine the graphicinformation BMP of the node by providing a link to an image file (e.g.,a bitmap) that corresponds to the type information determined for thenode object. Further, in operation S625, for each node object beingdefined in the simulation model file in operation S625, the simulationmodel generating apparatus 200 may set the paste ID value “PasteID” asthe ID of the link, identified in operation S560, that the node object(e.g., valve or check valve) is placed inline of (or on top of).

As was noted above, FIGS. 5-7 were described with reference to ascenario in which (i) the XML file received in operation S205 representspiping segments as objects, and (ii) according to the syntax of thesimulation model file generated in step S220, piping segments arerepresented as links that originate at a first node and terminate at asecond node, and each link may be a pump link or a flow link.

However, according to at least some example embodiments, if the XML filereceived in operation S205 and the syntax of the simulation model filegenerated in step S220 both describe piping segments using links, orboth describe piping segments as objects that can have more than twobranches, operation S520-S530 in FIG. 5 may be omitted, and thesimulation model generating apparatus 200 may proceed directly fromoperation S515 to operation S535, when the object is determined to be apiping segment in operation S515.

Further, if, according to the syntax of the simulation model filegenerated in step S220, pumps are described as node objects instead oflink objects, a node array may be created for the pump object inoperation S580 instead of a link array.

Further, if, according to the syntax of the simulation model filegenerated in step S220, on-link nodes are treated as endpoints in thesame manner as endpoint nodes, operations S620 and S625 in FIG. 6 may beomitted, and all node objects (including valves and check valves) may behandled by the simulation model generating apparatus 200 in accordancewith operation S610 and S615.

FIG. 8 is a flow chart illustrating an example of a simulation modelgenerating method. The simulation modeling method of FIG. 8 may beperformed by the simulation model generating apparatus 200. Thesimulation modeling method of FIG. 8 may include receiving and openingan XML file corresponding to a PID of a system, as is described ingreater detail below with reference to operations S805 and S810. The XMLfile may include information about attributes of the PID and informationabout attributes of components of the system. The simulation modelingmethod of FIG. 8 may further include extracting the information aboutthe attributes of the PID and storing the extracted information aboutthe attributes of the PID, as is discussed in greater detail below withreference to operation S815. The simulation modeling method of FIG. 8may further include identifying components of the system that aredescribed in the XML file, extracting information about the attributesof the identified components from the XML file, and storing theextracted information about the attributes of the identified components,as is discussed in greater detail below with reference to operationsS820-S840. The simulation modeling method of FIG. 8 may further includegenerating a simulation model page using syntax of a desired simulationmodeling software environment, based on the stored information about theattributes of the identified components, as is discussed in greaterdetail below with reference to operation S850.

In operation S805, the simulation model generating apparatus 200receives an XML file. The simulation model generating apparatus mayperform operation S805 in the same manner as that discussed above withrespect to operation S205 of FIG. 2. As an example, FIG. 8 will beexplained with respect to a scenario in which the simulation modelgenerating apparatus receives the XML file 400 of FIG. 4 in operationS805. According to at least some example embodiments, PID generatingsoftware used to create or access a PID of a system may export the PIDof the system in the form of the XML file received by the simulationmodel generating apparatus 200 in operation S805. FIG. 8 will beexplained with reference to a scenario in which, the PID 300 of FIG. 3is exported, by the PID generating software used to create or access thePID 300, as the XML file 400 received by the simulation model generatingapparatus 200 in operation S805. According to at least some exampleembodiments, the XML file 400 follows PID XML Standard ISO 15926.

In operation S810, the simulation model generating apparatus 200 opensthe XML file received in operation S805 in order to access the contentsof the received XML file. For example, in operation S810, the simulationmodel generating apparatus 200 opens the XML file 400.

In operation S815, the simulation model generating apparatus 200extracts, from the received XML file, dimensions of the PIDcorresponding to the received XML file, and stores the extractedinformation in a data structure referred to, herein, as a PIDcoord list.According to at least some example embodiments, the simulation modelgenerating apparatus 200 may generate the PIDcoord list by searchingthrough the XML file 400, finding the element that lists the dimensionsof the PID 300, creating an array or object data structure that storesthe dimensions of the PID 300 listed in the XML file 400, and storingthe created array or object in the PIDcoord list. For example, thesimulation model generating apparatus 200 may extract “X” and “Y”attributes of “Min” and “Max” sub-elements of an “Extent” sub-element ofa “Drawing” element included in the XML file 400, and store theextracted elements as PID coordinate object in the PIDcoord list. If anXML file includes information exported from more than one PID, thesimulation model generating apparatus 200 may create a PID coordinateobject for each PID represented in the XML file, the PIDcoord list mayinclude each of the create PID coordinate objects.

In operation S820, the simulation model generating apparatus 200extracts, from the received XML file, information about equipmentcomponents described in the XML file, and stores the extractedinformation in a data structure referred to, herein, as a EQcoord list.The EQcoord list may be generated based on a data structure referred to,herein, as a PIDequip list in a manner that will now be discussed ingreater detail below.

For example, according to at least some example embodiments, inoperation S820, the simulation model generating apparatus 200 searchesthrough the XML file 400, and finds each “Equipment” element listed inthe XML file 400. Further, according to at least some exampleembodiments, in operation S820, for each “Equipment” element found inthe XML file 400, the simulation model generating apparatus 200 extractsattribute information about the “Equipment” element from the XML file400, creates a component object data structure which includes elementscorresponding to the attributes of the “Equipment” element extractedfrom the XML file, and stores the created component object in thePIDequip list. According to at least some example embodiments, thestructure of the component array shown in Table 1 discussed above withreference to operations S210 and S215 of FIG. 2 is an example of thestructure of the component objects the simulation model generatingapparatus 200 creates for each “Equipment” element found in the XML file400 in operation S820. For example, according to at least some exampleembodiments, each component object created by the simulation modelgenerating apparatus 200 in operation S820 may be created in the samemanner as that described above with respect to operations S210 and S215,and the component array shown in Table 1.

Further, in operation S820, the simulation model generating apparatus200 may convert the attributes included in each of the component objectsincluded in the PIDequip list into a series of strings, and store theseries of strings in the EQcoord list along with text identifying theattributes included in each string.

One of the attributes included in each of the component objects is theID attribute, which may be, for example, a 32-hexadecimal numberidentifier that uniquely identifies the component for which thecomponent object was created. Some component objects further include IDattributes that identify sub-components of the component for which thecomponent object was created (e.g., the nozzle IDSs of nozzles includedin a filter component shown in FIG. 4). In operation S820, for eachcomponent object included in the PIDequip list, the simulation modelgenerating apparatus 200 may read the 32-hexadecimal number identifierof the component object (and the 32-hexadecimal number identifiers ofany corresponding sub-components), and convert the unique 32-hexadecimalnumber identifiers into n-digit unique identifier, where ‘n’ is apositive integer. For example, the simulation model generating apparatus200 may read the 32-hexadecimal number identifier of each componentobject included in the PIDequip list, and convert the unique32-hexadecimal number identifier into a 4-digit unique identifier (e.g.,a unique identifier that is a 4-digit decimal (i.e., base-10) number).According to at least some example embodiments, the simulation modelgenerating apparatus 200 may start with the 4-digit value “0001” andincrement the 4-digit value, for example, by 1, for every new uniqueidentification value corresponding to every unique 32-hexadecimal numberidentifier of every component object generated by the simulation modelgenerating apparatus 200. According to at least some exampleembodiments, the simulation model generating apparatus 200 may generatethe EQcoord list in operation S820 by storing the unique 4-digit valuesgenerated in operation S820 in the EQcoord list as unique IDscorresponding to each of the component objects and sub-components of thePIDequip list, in place of the 32-hexadecimal number identifiers fromwhich the unique 4-digit values were converted.

In operation S825, the simulation model generating apparatus 200extracts, from the received XML file, information about piping networkcomponents described in the XML file, and stores the extractedinformation in a data structure referred to, herein, as a PIDpiperunlist.

For example, according to at least some example embodiments, inoperation S825, the simulation model generating apparatus 200 searchesthrough the XML file 400, and finds each “PipingNetworkSegment” elementlisted in the XML file 400. Further, according to at least some exampleembodiments, in operation S825, for each “PipingNetworkSegment” elementfound in the XML file 400, the simulation model generating apparatus 200extracts attribute information about the “PipingNetworkSegment” elementfrom the XML file 400, creates a component object data structure whichincludes elements corresponding to the attributes of the“PipingNetworkSegment” element extracted from the XML file, and storesthe created component object in the PIDpiperun list. According to atleast some example embodiments, the structure of the component arrayshown in Table 1 discussed above with reference to operations S210 andS215 of FIG. 2 is an example of the structure of the component objectsthe simulation model generating apparatus 200 creates for each“PipingNetworkSegment” element found in the XML file 400 in operationS825. For example, according to at least some example embodiments, eachcomponent object created by the simulation model generating apparatus200 in operation S825 may be created in the same manner as thatdescribed above with respect to operations S210 and S215, and thecomponent array shown in Table 1.

In operation S830, the simulation model generating apparatus 200 mayconvert the attributes included in each of the component objectsincluded in the PIDpiperun list into a series of strings, and store theseries of strings in a data structure referred to, herein, as aPIDpiperunconn list along with text identifying the attributes includedin each string.

According to at least some example embodiments, in operation S830, foreach component object included in the PIDpiperun list, the simulationmodel generating apparatus 200 may read the 32-hexadecimal numberidentifier of the component object (and the 32-hexadecimal numberidentifiers of any corresponding sub-components), and convert the unique32-hexadecimal number identifiers into n-digit unique identifiers, forexample, in the same manner discussed above with respect to operationS820. According to at least some example embodiments, the simulationmodel generating apparatus 200 may generate the PIDpiperunconn list inoperation S830 by storing the unique 4-digit values generated inoperation S230 in the PIDpiperunconn list as unique IDs corresponding toeach of the component objects and sub-components of the PIDpiperun list,in place of the 32-hexadecimal number identifiers from which the unique4-digit values were converted.

In operation S835, the simulation model generating apparatus 200extracts, from the received XML file, information about processinstrument components described in the XML file, and stores theextracted information in a data structure referred to, herein, as aProcInst list.

For example, according to at least some example embodiments, inoperation S835, the simulation model generating apparatus 200 searchesthrough the XML file 400, and finds each “ProcessInstrument” elementlisted in the XML file 400. Further, according to at least some exampleembodiments, in operation S835, for each “ProcessInstrument” elementfound in the XML file 400, the simulation model generating apparatus 200extracts attribute information about the “ProcessInstrument” elementfrom the XML file 400, creates a component object data structure whichincludes elements corresponding to the attributes of the“ProcessInstrument” element extracted from the XML file, and stores thecreated component object in the ProcInst list. According to at leastsome example embodiments, the structure of the component array shown inTable 1 discussed above with reference to operations S210 and S215 ofFIG. 2 is an example of the structure of the component objects thesimulation model generating apparatus 200 creates for each“ProcessInstrument” element found in the XML file 400 in operation S835.For example, according to at least some example embodiments, eachcomponent object created by the simulation model generating apparatus200 in operation S835 may be created in the same manner as thatdescribed above with respect to operations S210 and S215, and thecomponent array shown in Table 1.

In operation S840, the simulation model generating apparatus 200 mayconvert the attributes included in each of the component objectsincluded in the ProcInst list into a series of strings, and store theseries of strings in a data structure referred to, herein, as aProcInstList list along with text identifying the attributes included ineach string.

According to at least some example embodiments, in operation S840, foreach component object included in the ProcInst list, the simulationmodel generating apparatus 200 may read the 32-hexadecimal numberidentifier of the component object (and the 32-hexadecimal numberidentifiers of any corresponding sub-components), and convert the unique32-hexadecimal number identifiers into n-digit unique identifiers, forexample, in the same manner discussed above with respect to operationS820. According to at least some example embodiments, the simulationmodel generating apparatus 200 may generate the ProcInstList list inoperation S840 by storing the unique 4-digit values generated inoperation S230 in the ProcInstList list as unique IDs corresponding toeach of the component objects and sub-components of the ProcInst list,in place of the 32-hexadecimal number identifiers from which the unique4-digit values were converted.

After operation S840, the simulation model generating apparatus 200 maycreate a simulation model page and populate the simulation model pagewith simulation node objects, link objects and/or instrumentationobjects based on each of the components defined in each of the componentobject lists (e.g., the EQcoord list, the PIDpiperunconn list, and theProcInstList list). For example, the simulation model generatingapparatus 200 may loop through the EQcoord list and create a simulationnode object for each component object included in the EQcoord list,using the syntax of the desired simulation modeling softwareenvironment. Further, the simulation model generating apparatus 200 mayloop through the PIDpiperunconn list and create a simulation link objectfor each component object included in the PIDpiperunconn list, using thesyntax of the desired simulation modeling software environment. Further,the simulation model generating apparatus 200 may loop through theProcInstList list and create a simulation instrument object for eachcomponent object included in the ProcInstList list, using the syntax ofthe desired simulation modeling software environment. The simulationmodel generating apparatus 200 may populate the simulation model pagewith the created simulation node objects, link objects and/orinstrumentation objects. The operations of creating the simulation modelpage and populating the simulation model page with simulation nodeobjects and link objects will be discussed in greater detail below withreference to operations S845 and S847.

For example, in operation S845, the simulation model generatingapparatus 200 may identify a number and position of nodes, and inoperation S847 the simulation model generating apparatus 200 mayidentify links. According to at least some example embodiments, thesimulation model generating apparatus 200 performs operation S845 in thesame manner discussed above with respect to operations S605-S625 of FIG.6, and performs operation S847 in the same manner discussed above withrespect to operations S705-S725 of FIG. 7. For example, the EQcoord listcreated in operation S820 may correspond to the endpoint and on-linknode array lists discussed above with reference to FIGS. 5 and 6.Further, the PIDpiperunconn and ProcInstList lists created in operationS830 and S840 may correspond to the link array list discussed above withreference to FIGS. 5 and 7. Accordingly, in operations S845 and S847,the simulation model generating apparatus 200 generates and populates asimulation model file according to the syntax of the desired simulationmodeling software environment.

After operations S845 and S847, in operation S850, a simulation modelpage is output. For example, in operation S850, the simulation modelfile generated in operations S845 and S847 may be imported into (or,exported to) the desired simulation modeling software environment as asimulation model page. For example, according to at least some exampleembodiments, in operation S850, the simulation model generatingapparatus 200 may provide the simulation model page generated inoperations S845 and S847 to an application corresponding to the desiredsimulation modeling software environment. Further, according to at leastsome example embodiments, in operation S850, the simulation modelgenerating apparatus 200 may output the simulation model page generatedin operations S845 and S847 to a destination (e.g., folder) chosen by auser of the simulation model generating apparatus 200, with or withoutproviding the simulation model page to an application corresponding tothe desired simulation modeling software environment.

While a number of example embodiments have been disclosed herein, itshould be understood that other variations may be possible. Suchvariations are not to be regarded as a departure from the spirit andscope of the present disclosure, and all such modifications as would beobvious to one skilled in the art are intended to be included within thescope of the following claims.

What is claimed:
 1. A method of facilitating modeling of a system, themethod comprising: receiving, at a processor, an extensible markuplanguage (XML) file corresponding to a piping and instrumentationdiagram (PID) of the system; identifying, by the processor, componentsof the system that are described in the XML file, the XML file includinginformation about attributes of the identified components; storing, bythe processor, the information about the attributes of the identifiedcomponents; and generating, by the processor, a simulation model pageusing syntax of a simulation modeling software environment, based on thestored information about the attributes of the identified components. 2.The method of claim 1, wherein the system is a process plant system. 3.The method of claim 2, wherein the XML file follows PID XML Standard ISO15926.
 4. The method of claim 1, wherein the identifying includes, foreach identified component, identifying, in the XML file, an XML elementcorresponding to the component.
 5. The method of claim 4, furthercomprising: generating, by the processor, for each identified XMLelement, a component object data structure corresponding to theidentified XML element.
 6. The method of claim 5, further comprising:for each identified XML element, extracting, by the processor, attributeinformation of the identified XML element from the XML file.
 7. Themethod of claim 6 wherein the storing comprises: for each generatedcomponent object data structure, storing, as one or more elements of thegenerated component object data structure, the attribute informationextracted from the identified XML element to which the generatedcomponent object data structure corresponds.
 8. The method of claim 1,wherein the storing comprises: generating a list of strings defining theidentified components, the list of strings including information basedon the information about the attributes of the identified components. 9.The method of claim 8, wherein the generating of the simulation modelpage comprises: reading from the list of strings, by the processor,attributes of each component defined the list of strings; creating asimulation object for each component defined by the list of strings,based on the read attributes; and populating the simulation model pagewith the simulation objects created for the components defined by thelist of strings.
 10. A simulation model generating apparatus comprising:memory storing computer-executable instructions; and one or moreprocessors configured to execute the computer-executable instructionssuch that the one or more processors are configured to performoperations including, receiving an extensible markup language (XML) filecorresponding to a piping and instrumentation diagram (PID) of a system,identifying components of the system that are described in the XML file,the XML file including information about attributes of the identifiedcomponents, storing the information about the attributes of theidentified components, and generating a simulation model page usingsyntax of a simulation modeling software environment, based on thestored information about the attributes of the identified components.11. The apparatus of claim 10, wherein the system is a process plantsystem.
 12. The apparatus of claim 11, wherein the XML file follows PIDXML Standard ISO
 15926. 13. The apparatus of claim 10, wherein the oneor more processors are configured to execute the computer-executableinstructions such that the identifying includes, for each identifiedcomponent, identifying, in the XML file, an XML element corresponding tothe component.
 14. The apparatus of claim 13, wherein the one or moreprocessors are configured to execute the computer-executableinstructions such that the one or more processors are further configuredto generate, for each identified XML element, a component object datastructure corresponding to the identified XML element.
 15. The apparatusof claim 14, wherein the one or more processors are configured toexecute the computer-executable instructions such that the one or moreprocessors are further configured to, for each identified XML element,extract attribute information of the identified XML element from the XMLfile.
 16. The apparatus of claim 15 wherein the one or more processorsare configured to execute the computer-executable instructions such thatthe storing includes, for each generated component object datastructure, storing, as one or more elements of the generated componentobject data structure, the attribute information extracted from theidentified XML element to which the generated component object datastructure corresponds.
 17. The apparatus of claim 10, wherein the one ormore processors are configured to execute the computer-executableinstructions such that the storing includes, generating a list ofstrings defining the identified components, the list of stringsincluding information based on the information about the attributes ofthe identified components.
 18. The apparatus of claim 17, wherein theone or more processors are configured to execute the computer-executableinstructions such that the generating of the simulation model pageincludes, reading, from the list of strings, attributes of eachcomponent defined the list of strings, creating a simulation object foreach component defined by the list of strings, based on the readattributes, and populating the simulation model page with the simulationobjects created for the components defined by the list of strings.